Digital cable TV receiver, diagnosis method for the same, and data structure of HDMI status report

ABSTRACT

A digital cable TV receiver includes a POD module and a host device. The host device includes a controller and a HDMI port linked to a first peripheral device. When the controller receives a diagnostic request for HDMI status from the POD module, it generates a HDMI status report and transmits the DVI status report to the POD module. The HDMI status report includes HDMI status information associated with the first peripheral device. If the host device further includes a DVI port linked to a second peripheral device and receives a diagnostic request for HDMI/DVI status from the PDO module, it generates a HDMI/DVI status report and transmits the HDMI/DVI status report to the POD module. The HDMI/DVI status report includes HDMI status information associated with the first peripheral device and DVI status information associated with the second peripheral device.

This application claims the benefit of the Korean Patent Application No.10-2004-0061804, filed on Aug. 5, 2004, which is hereby incorporated byreference as if fully set forth herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a cable broadcast program receiver andtransmitter, and more particularly, to a digital cable TV receiver, adiagnosis method for the same, and a data structure of a HDMI statusreport, wherein the program receiver provides status information of aplurality of peripheral devices connected to the cable broadcast programreceiver (or digital cable TV receiver) through a DVI link or a HDMIlink.

2. Discussion of the Related Art

Generally, a Digital Visual Interface (DVI) is a transmission standardestablished by a consortium called the Digital Display Working Group(DDWG), which has been created by a group of leaders in the computerindustry. The DVI is used to digitally connect a personal computer (PC)to a flat monitor. More specifically, the DVI is a standard fordigitally connecting signals exchanged between the PC and the monitor.The DVI has mainly been adopted to peripheral devices that are used bybeing connected to a PC, such as personal computers, office projectors,general plasma displays, electric boards. And, recently, the DVI hasalso been adopted in digital television (TV) receivers and cable digitaltelevision (TV) receivers. Before the DVI standard was developed,digital signals were exchanged by a complicated process. First, the PCcreates digital data. Then, even though the digital display device iscapable of receiving digital data, the digital data transmitted from thePC is converted to analog data, which is converted back to digital dataand then transmitted to the digital display device. Therefore, in orderto avoid such a complicated process, the DVI standard has been developedto allow the digital data created from the PC to be digitallytransmitted directly to the display device through a cable. In the DVIstandard, digital broadcast signals that are not compressed aretransmitted in a single direction.

A High-Definition Multimedia Interface (HDMI) is a transmission standardenabling digital audio and video signals to be connected by a singlecable without compression. More specifically, since a multiple channeltransmission (5.1 channel) can be performed in case of the audio signal,it will be more accurate to refer to the interface as a multimediainterface, rather than a video interface. In other words, the differencebetween the HDMI and the DVI is that the HDMI is smaller than the DVI,has a High-bandwidth Digital Content Protection (HDCP) coding functionsprovided therein, and supports multiple channel audio. Therefore, theHDMI standard enables the DVI to be adopted in both audio and videoelectronic appliances, whereas the DVI standard can adopt the DVIinterface only in video electronic appliances. And so, since the HDMI isconsidered to be an updated version of the DVI, the related industry isbeginning to renew the Input/Output interfaces applied to digitaltelevisions (TVs) and Set-Top boxes from the DVI standard to the HDMIstandard. Since the HDMI standard is an integration of the DVI-basedHDCP and audio signals (EIA/CEA-861), the HDMI standard may also bereferred to as DVI-HDMI. However, in order to make a clear distinctionbetween the HDMI and the DVI in the present invention, the HDMI standardwill simply be referred to as “HDMI”. Furthermore, the DVI/HDMIdescribed in the present invention refers to “DVI and/or HDMI” and isdistinguished from the term “DVI-HDMI”.

Meanwhile, a cable broadcast system broadly includes a cable broadcaststation (or cable TV station) and a cable broadcast program receiver (ordigital cable TV receiver). Herein, the cable broadcast station is atransmitting and receiving end transmitting cable broadcast programs,and the cable broadcast program receiver receives the transmitted cablebroadcast program. The cable broadcast station may be referred to a SOhead-end or a MSO head-end. The SO refers to a System Operator (SO),which is a Korean Cable System Operator (i.e., the Local Cable TV SystemOperator), and the MSO refers to a Multiple System Operator (MSP), whichis a group of system operators.

Moreover, the cable broadcast program receiver adopts an open cable,wherein a Point of Deployment (POD) module including a ConditionalAccess (CA) system is separated (or detached) from the main body. Forexample, the POD module uses a Personal Computer Memory CardInternational Association (PCMCIA) card which can be mounted onto andseparated from a main body slot of the cable broadcast program receiver.Therefore, the POD module may also be referred to as a cable card, andthe main body, wherein the POD module is inserted, may also be referredto as a host. For example, a Digital Built-in TV or a Digital Ready TVcorresponds to the host, and a combination of the host and the PODmodule is referred to as the cable broadcast program receiver. At thispoint, the host may be connected to other peripheral devices (e.g., aDigital TV, a DVD player, a digital camera/camcorder, a Set-Top box,etc.) through one of a DVI link and a HDMI link. More specifically, oneor more DVI ports or HDMI ports may exist within the host. Accordingly,a plurality of peripheral devices may be connected to the host through aDVI link or a HDMI link.

Meanwhile, in the open cable standard, wherein the POD module isseparated from the main body, a diagnostic function is provided to alloweach status of the host to be monitored. The diagnostic function checksvarious statuses, such as operation status of the host and connectionstatus of the peripheral devices. For example, in the STCE 28 2004standard, the Generic Diagnostic Protocol is defined in a host-PODinterface resource layer. The Generic Diagnostic Protocol has beendefined to enable each status information of the host to be monitored inreal-time through local broadcast stations (local, user) or cablebroadcast stations (remote, MSO head-end). Herein, the GenericDiagnostic Protocol defines the following diagnostics shown in Table 1below: TABLE 1 Diagnostic ID Diagnostic 00 Set-Top memory allocation 01Software version 02 Firmware version 03 MAC status 04 FAT status 05 FDCstatus 06 Current Channel Report 07 1394 Port 08 DVI status 09˜FFReserved for future use

More specifically, when a request for diagnostic is transmitted to thehost from the POD module, and when the Diagnostic ID is ‘08’, thedetails of the request consist of verifying the DVI status of the hostand reporting the verified DVI status to the POD module.

FIG. 1 illustrates an example of a Diagnostic Confirm Object Syntaxthrough which the host verifies a DVI status and transmits a report tothe POD module. More specifically, the POD module parses aDiagnostic_cnf APDU (i.e., a Diagnostic Confirm Object Syntax)transmitted from the host and parses a report syntax corresponding toeach Diagnostic ID, thereby extracting the status information for eachdiagnostic item. For example, in the Diagnostic Confirm Object Syntax ofFIG. 1, when the parsed Diagnostic ID is ‘0x08’, then a DVI StatusReport Syntax is parsed, thereby extracting the DVI status information.In other words, when the POD module transmits a diagnostic request(Diagnostic_req APDU) to the host requesting the host to verify the DVIstatus and to report the verified results back to the POD module, thehost checks the DVI status and transmits the result back to the PODmodule in the form of a DVI Status Report Syntax (Diagnostic_cnf APDU).Therefore, according to the Generic Diagnostic Protocol shown in FIG. 1,the POD module cannot request a HDMI status information from the host,and the host cannot provide any HDMI status information to the PODmodule.

SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to a digital cable TVreceiver, a diagnosis method for the same, and a data structure of aHDMI status report that substantially obviate one or more problems dueto limitations and disadvantages of the related art.

An object of the present invention is to provide a digital cable TVreceiver, a diagnosis method for the same, and a data structure of aHDMI status report that can transmit a request a HDMI status informationfrom a POD module and that can verify the HDMI status and transmit theverified result to the POD module from a host.

Another object of the present invention is to provide a digital cable TVreceiver, a diagnosis method for the same, and a data structure of aHDMI status report that can expand a Generic Diagnostic Protocol definedin a SCTE 28 standard (wherein, “SCTE” stands for the Society of CableTelecommunications Engineers), so that a POD module can transmit arequest for a HDMI status information.

Another object of the present invention is to provide a digital cable TVreceiver, a diagnosis method for the same, and a data structure of aHDMI status report that can expand a Generic Diagnostic Protocol definedin a SCTE 28 standard, so that a host can verify the HDMI status andtransmit the verified result to the POD module.

A further object of the present invention is to provide a digital cableTV receiver, a diagnosis method for the same, and a data structure of aHDMI status report that can expand a Generic Diagnostic Protocol definedin a SCTE 28 standard, so that all status information can be transmittedto the POD module, when a plurality of peripheral devices issimultaneously connected to a host through DVI/HDMI ports.

Additional advantages, objects, and features of the invention will beset forth in part in the description which follows and in part willbecome apparent to those having ordinary skill in the art uponexamination of the following or may be learned from practice of theinvention. The objectives and other advantages of the invention may berealized and attained by the structure particularly pointed out in thewritten description and claims hereof as well as the appended drawings.

To achieve these objects and other advantages and in accordance with thepurpose of the invention, as embodied and broadly described herein, adigital cable TV receiver includes a POD module, and a host devicecomprising a controller and a HDMI port linked to a peripheral device,wherein the controller generates a HDMI status report and transmits theHDMI status report to the POD module when a diagnostic request for HDMIstatus is received from the POD module, the HDMI status reportcomprising HDMI status information associated with the peripheraldevice.

In another aspect of the present invention, a diagnostic method for adigital cable TV receiver includes receiving a diagnostic request forHDMI status from a POD module, and performing a diagnostic function inresponse to the diagnostic request by generating a HDMI status reportand transmitting the HDMI status report to the POD module, the HDMIstatus report comprising HDMI status information associated with aperipheral device which is linked to a HDMI port.

In another aspect of the present invention, a data structure of a HDMIstatus report for use in a digital cable TV receiver includes aconnection status field indicating whether a connection exists on a HDMIport, and HDMI status information associated with a peripheral devicelinked to the HDMI port.

In another aspect of the present invention, a digital cable TV receiverincludes a POD module, and a host device comprising a controller, a HDMIport linked to a first peripheral device, and a DVI port linked to asecond peripheral device, the controller generating a HDMI/DVI statusreport and transmits the HDMI/DVI status report to the POD module when adiagnostic request for HDMI/DVI status is received from the POD module,the HDMI/DVI status report comprising HDMI status information associatedwith the first peripheral device and DVI status information associatedwith the second peripheral device.

In another aspect of the present invention, a diagnostic method for adigital cable TV receiver includes receiving a diagnostic request forHDMI/DVI status from a POD module, and performing a diagnostic functionin response to the diagnostic request by generating a HDMI/DVI statusreport and transmitting the HDMI/DVI status report to the POD module,the HDMI/DVI status report comprising HDMI status information associatedwith a first peripheral device which is linked to a HDMI port and DVIstatus information associated with a second peripheral device which islinked to a DVI port.

In a further aspect of the present invention, a data structure of aHDMI/DVI status report for use in a digital cable TV receiver includes aconnection status field indicating whether a connection exists on anyone of a HDMI port and a DVI port, HDMI status information associatedwith a first peripheral device linked to the HDMI port, and DVI statusinformation associated with a second peripheral device linked to the DVIport.

It is to be understood that both the foregoing general description andthe following detailed description of the present invention areexemplary and explanatory and are intended to provide furtherexplanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates an example of a Diagnostic_cnf syntax of a generalSTCE standard;

FIG. 2 illustrates an example of a message exchange protocol in aGeneric Diagnostic according to the present invention;

FIG. 3 illustrates an example of an expanded Diagnostic_cnf syntax ofthe STCE standard according to the present invention;

FIGS. 4A to 4C illustrate a HDMI_DVI_status_report( ) syntax accordingto an embodiment of the present invention;

FIG. 5 illustrates an example of a digital cable TV receiver accordingto the present invention;

FIG. 6 illustrates a flow chart of process steps for creating andtransmitting DVI/HDMI status information according to an embodiment ofthe present invention;

FIGS. 7A to 7C illustrate a HDMI_status_report( ) syntax according toanother embodiment of the present invention; and

FIG. 8 illustrates a flow chart of process steps for creating andtransmitting HDMI status information according to another embodiment ofthe present invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts. In addition,although the terms used in the present invention are selected fromgenerally known and used terms, some of the terms mentioned in thedescription of the present invention have been selected by the applicantat his or her discretion, the detailed meanings of which are describedin relevant parts of the description herein. Furthermore, it is requiredthat the present invention is understood, not simply by the actual termsused but by the meaning of each term lying within.

The present invention relates to requesting a host from a POD module toverify a HDMI status and to report the result to the POD module, andalso relates verifying the HDMI status information from the host andtransmitting the result back to the POD module. As an example, in orderto carry out such process, the above-described related art GenericDiagnostic Protocol is expanded. Herein, the expansion of the GenericDiagnostic Protocol is for maintaining compatibility with all cablebroadcast program receivers (or digital cable TV receivers) adopting theSCTE 28 standard. As described above, the Generic Diagnostic Protocolhas been defined to enable each status information of the host to bemonitored in real-time through local broadcast stations (local, user) orcable broadcast stations (remote, MSO head-end).

FIG. 2 illustrates an example of a message exchange protocol in aGeneric Diagnostic according to the present invention. In this example,the POD module transmits a diagnostic request (Diagnostic_req APDU) tothe host, and the host transmits the diagnostic result (Diagnostic_cnfAPDU) to the POD module. More specifically, when the POD module receivesa diagnostic command, the POD module transmits a diagnostic request(Diagnostic_req APDU) to the host. Herein, the diagnostic request may betransmitted to the POD module from the cable broadcast station, or maybe inputted directly to the POD module by a user using a remotecontroller. Alternatively, even when a diagnostic request is nottransmitted from the POD module, the system status may be regularly (orperiodically) verified from the host, and the corresponding results maybe transmitted to the POD module.

For example, under the assumption that a cable broadcast program is notdisplayed normally, and if a diagnostic command option is provided,which can be selected by a user through a remote controller or a menuscreen, the user may be able to select the diagnostic command option byusing the remote controller or the menu screen. If the user is in anenvironment in which he/she is unable to select the diagnostic commanddirectly, the user would contact the cable broadcast station by phone orthe Internet. Thereafter, the cable broadcast station will transmit adiagnostic command to the POD module of the corresponding digital cableTV receiver.

Meanwhile, the host receiving the diagnostic request (Diagnostic_reqAPDU) from the POD module verifies the status of each diagnostic itemcorresponding to the Diagnostic ID. Then, the host reports the verifiedresults (Diagnostic_cnf APDU) to the POD module. The POD module mayeither transmit the verified results (Diagnostic_cnf APDU) received fromthe host to the cable broadcast station or may display the verifiedresults (Diagnostic_cnf APDU) to the user through an OSD Diagnosticapplication of the host. For example, if a bi-directional transmissioncan be performed between the cable broadcast station (or cable TVstation) and the cable broadcast program receiver (or digital cable TVreceiver), the diagnostic results are transmitted to the cable broadcaststation through 00B. At this point, the diagnostic result may besimultaneously transmitted to the cable broadcast station and displayedon the TV screen through the OSD Diagnostic application. In case thedigital cable TV receiver is mono-directional, the diagnostic result isdisplayed onto the TV screen through the OSD Diagnostic application.And, when the user notifies the cable broadcast station of the displayedcontents, the cable broadcast station performs operations in accordancewith the diagnostic results (e.g., door-to-door or wireless/wiredafter-services).

In the present invention, the Generic Diagnostic Protocol is expanded sothat the POD module can request the host to perform a diagnostic of theDVI/HDMI status, and also that the host can verify the DVI/HDMI statusand transmit the corresponding status information back to the PODmodule. More specifically, the definition of the diagnostic items forthe Diagnostic ID being assigned as 0x08 within the Generic DiagnosticProtocol is expanded as shown in Table 2 below. And, the DVI StatusReport Syntax is expanded as a DVI/HDMI Status Report Syntax shown inFIGS. 4A to 4C. In other words, the POD module includes a Diagnostic ID(i.e., 0x08) requesting a DVI/HDMI status to be diagnosed within theDiagnostic_req APDU and transmits the Diagnostic_req APDU to the host.Subsequently, the host includes all status information of all peripheraldevices connected to the host by either one of the DVI link and the HDMIlink within the Diagnostic_cnf APDU and transmits the Diagnostic_cnfAPDU back to the POD module. Table 2 shows the Diagnostic items definedin the expanded Generic Diagnostic Protocol according to the presentinvention and the IDs assigned for each Diagnostic item. TABLE 2Diagnostic ID Diagnostic 00 Set-Top memory allocation 01 Softwareversion 02 Firmware version 03 MAC status 04 FAT status 05 FDC status 06Current Channel Report 07 1394 Port

09˜FF Reserved for future use

Herein, the Diagnostic ID and item marked in bold italic characters arenewly defined within the Generic Diagnostic Protocol according to thepresent invention. More specifically, in the new definition, when theDiagnostic ID is 0x08, all of the DVI statuses and HDMI statuses arerequested to be verified and reported. The above-described Table 2 showsan embodiment having a request for diagnosing HDMI status added to theDiagnostic ID requesting the DVI status to be diagnosed.

FIG. 3 illustrates an example of a Diagnostic Confirm Object Syntaxaccording to the present invention, which verifies the DVI or HDMI linkfrom the host and reports the result to the POD module. Morespecifically, when the Diagnostic ID is 0x08, theHMDI_DVI_status_report( ) of FIGS. 4A and 4C is parsed, and the statusinformation of the DVI links and the HMDI links are extracted.

FIGS. 4A to 4C illustrate an example of a DVI/HDMI Status Report Syntaxof the General Diagnostic Protocol according to the present invention.More specifically, with the exception of a connection_status field, ahost_HDCP_status field, a Device_HDCP_status field, a video_formatfield, a horizontal_lines field, a vertical_lines field, a scan_ratefield, an aspect_ratio field, and a prog_inter_type field, the remainingfields are status information that are newly defined in the presentinvention. Nevertheless, the definition for each of the above-mentionedfields is also expanded to the HDMI link. Hereinafter, the DVI/HDMIStatus Report Syntax of FIGS. 4A to 4C will now be described in detail.

First of all, the connection_status field indicates whether a connectionexists on a DVI port or a HDMI port of the host. And, when theconnection_status field value is ‘00₂’, then no DVI or HDMI link (orconnection) exists. Therefore, the DVI/HDMI status information can onlybe created when the connection_status field value is not equal to ‘00₂’.More specifically, an IF conditional statement ‘if(connection_status!=0x00) { }’ can be performed only when the connection_status fieldvalue is not equal to ‘00₂’. Additionally, a connection_count field isallocated with 8 bits and indicates the number of DVI/HDMI links, whenperipheral devices are connected to the host by DVI link or HDMI link.For example, when a DVD Player is connected to the host by a DVI linkand a Set-Top box is connected to the host by a HDMI link, theconnection_status field value is equal to ‘2’.

Moreover, a FOR loop statement ‘for(i=0; i<connection_count; i++) { }’,which is repeatedly performed as much as the connection_status fieldvalue, is used for transmitting all status information to the PODmodule, when at least one or, most particularly, a plurality ofperipheral devices are connected to the host by DVI/HDMI link. Thenumber of repetition of the FOR loop is identical to theconnection_count field value, which indicates the number of peripheraldevices connection to the host by DVI/HDMI link. For example, when theconnection_count field value is equal to ‘2’, the FOR loop is repeatedtwice. In other words, each time the FOR loop is performed, a statusinformation for the HDMI link is created and transmitted to the PODmodule. Therefore, when the FOR loop is repeated twice, the statusinformation for a plurality of DVI/HDMI links is created and transmittedto the POD module.

Hereinafter, the fields that will now be described are all locatedwithin the repetition statement configured with the FOR loop. Theconnection_no field is allocated with 8 bits and is defined to indicatethe order of the DVI/HDMI link. More specifically, the order consists ofthe order of the DVI/HDMI links having their current status informationcreated and transmitted, when a plurality of peripheral devices isconnected to the host by DVI link or HDMI link. In addition, aconnection_mode field is allocated with one (1) bit and indicateswhether the status information that is currently being created in theFOR loop corresponds to a DVI link or a HDMI link. For example, when aperipheral device is currently connected to the host by HDMI link, theconnection_mode field value within the FOR loop is set to ‘1’.Conversely, when the connection_mode field value is ‘0’, this indicatesthat the peripheral device is currently connected to the host by DVIlink. The connection_type field is allocated with 2 bits. Herein, theconnection_type field indicates the connection type between thecorresponding peripheral device and the host for each DVI/HDMI link. Inother words, the connection_type field indicates whether the DVI/HDMIport of the host connected to the corresponding peripheral device is aDVI/HDMI Input port, a DVI/HDMI Output port or a DVI/HDMI Input/Outputport. For example, ‘00₂’ indicates the DVI/HDMI Input port (i.e., aninput connection only), ‘01₂’ represents the DVI/HDMI Output port (i.e.,an output connection only), and ‘10₂’ indicates the DVI/HDMIInput/Output port (i.e., an input/output connection). Furthermore, ‘11₂’represents an unused (or reserved) status.

The host_HDCP_status field indicates whether a HDCP is enabled withinthe DVI/HDMI link. (Herein, ‘HDCP’ stands for a High-bandwidth DigitalContent Protection standard.) For example, when the host_HDCP_statusfield value is ‘00₂’, the HDCP is not enabled. The Device_HDCP_statusfield indicates the HDCP status of the peripheral device connected tothe host through the DVI/HDMI port. The video_format field indicates thecurrent video format used on the DVI/HDMI port. The horizontal_linesfield, the vertical_lines field, the scan_rate field, the aspect_ratiofield, and the prog_inter_type field create information corresponding tothe video format within the DVI/HDMI link.

The fields that will now be defined correspond to HDMI statusinformation that are created when the peripheral device is connected tothe host by HDMI link, i.e., when the current connection_mode fieldvalue within the FOR loop is equal to ‘1’. Anauxiliary_information_status field is allocated with 5 bits and isdefined to indicate the status information of the peripheral deviceconnected to the host by HDMI link. Hereinafter, a detailed descriptionof the definition for each auxiliary_status_field value will now follow.

For example, when the value is 00000₂, Auxiliary information (auxiliaryinformation, only video format) does not exist. When the value is00001₂, an Auxiliary Video Information (AVI) InfoFrame informationexists, and when the value is 00010₂, an AUDIO InfoFrame informationexists. Additionally, when the value is 00100₂, a Source ProductDescription (SPD) InfoFrame information exists, and when the value is01000₂, an MPEG source InfoFrame information exists. Furthermore, whenthe value is 10000₂, a General Control (GC) InfoFrame informationexists. Therefore, when the value is 00011₂, both the AVI InfoFrameinformation and the AUDIO InfoFrame information exist. And, similarly,when the value is 11111₂, all of the AVI InfoFrame information, theAUDIO InfoFrame information, the SPD InfoFrame information, the MPEGsource InfoFrame information, and the GC InfoFrame information exist.For example, when a DVD Player is currently connected to the host byHDMI link, and when the AVI information, the AUDIO information, and theMPEG information are transmitted, the auxiliary_information_status fieldvalue is equal to ‘01011₂’. Moreover, the AVI information, the AUDIOinformation, and the MPEG information are created by an AVI_info{ }syntax, an AUDIO_info{ } syntax, and an MPEG_info{ } syntax. Therefore,when the auxiliary_information_status field value is parsed, and whenthe corresponding value is equal to ‘01011₂’, the AVI_info{ } syntax,the AUDIO_info{ } syntax, and the MPEG_info{ } syntax are parsed, so asto extract the AVI information, the AUDIO information, and the MPEGinformation.

Hereinafter, a detailed description of the process of creating the AVIinformation, the AUDIO information, the SPD information, the MPEGinformation, and the GC information will now follow. More specifically,when a logical product (or logical multiplication, logical AND) betweenthe auxiliary_information_status field value and 0x01 is equal to ‘1’,the current AVI information used within the HDMI port is created byusing the next newly defined AVI information fields within the AVI_info{} syntax. The newly defined AVI information fields include a versionfield, a color_space field, an active_format field, a bar_info field, ascan_info field, an aspect_ratio field, an active_format_aspect_ratiofield, a picture_scaling field, a video_id_code field, and apixel_repetition field.

The version field indicates the AVI InfoFrame version. The color_spacefield indicates the color space information associated with the video onthe current HDMI link. For example, each value indicates the following:

-   -   00₂=RGB;    -   01₂=YCbCr 4:2:2;    -   10₂=YCbCr 4:4:4; and    -   11₂=reserved.

The active_format field indicates the present active format associatedwith the video on the HDMI link. For example, each value indicates thefollowing:

-   -   0₂=No data; and    -   1₂=Active format information valid.

The bar_info field indicates the bar information associated with thevideo on the HDMI link. For example, each value indicates the following:

-   -   00₂=Bar data not valid;    -   01₂=Vertical Bar information valid;    -   10₂=Horizontal Bar information valid; and    -   11₂=Vertical and Horizontal Bar information valid.

The scan_info field indicates the scan information associated with thevideo on the HDMI link. For example, each value indicates the following:

-   -   00₂=No data;    -   01₂=Overscanned (television);    -   10₂=Underscanned (computer); and    -   11₂=reserved.

The colorimetry field indicates the colorimetry information associatedwith the video on the HDMI link. For example, each value indicates thefollowing:

-   -   00₂=No data;    -   01₂=SMPTE 170M or ITU601;    -   10₂=ITU709; and    -   11₂=reserved.

The aspect_ratio field indicates the picture aspect ratio associatedwith the video on the HDMI link. For example, each value indicates thefollowing:

-   -   00₂=No data;    -   01₂=4:3;    -   10₂=16:9; and    -   11₂=reserved.

The active_format_aspect_ratio field indicates the active format aspectratio associated with the video on the HDMI link. For example, eachvalue indicates the following:

-   -   1000₂=Same as picture aspect ratio;    -   1001₂=4:3 (Center);    -   1010₂=16:9 (Center);    -   1011₂=14:9 (Center); and    -   other=per DVB AFD active format field.

The picture_scaling field indicates the non-uniform picture scalingassociated with the video on the HDMI link. For example, each valueindicates the following:

-   -   00₂=No known non-uniform scaling;    -   01₂=Picture has been scaled horizontally;    -   10₂=Picture has been scaled vertically; and    -   11₂=Picture has been scaled horizontally and vertically.

The video_id_code field indicates the video identification code for CEAShort Descriptors associated with the video on the HDMI link. And, thepixel_repetition field indicates the pixel repetition associated withthe video on the HDMI link. For example, each value indicates thefollowing:

-   -   0000₂=No repetition (i.e., pixel sent once);    -   0001₂=pixel sent 2 times (i.e., repeated once);    -   0010₂=pixel sent 3 times;    -   0011₂=pixel sent 4 times;    -   0100₂=pixel sent 5 times;    -   0101₂=pixel sent 6 times;    -   0110₂=pixel sent 7 times;    -   0111₂=pixel sent 8 times;    -   1000₂=pixel sent 9 times;    -   1001₂=pixel sent 10 times; and    -   others=reserved.

Meanwhile, when a logical product (or logical multiplication, logicalAND) between the auxiliary_information_status field value and 0x02 isequal to ‘1’, the current audio information used within the HDMI port iscreated by using the next newly defined audio information fields withinthe AUDIO_info{ } syntax. In other words, when a logical product (orlogical multiplication, logical AND) between theauxiliary_information_status field value and 0x02 is equal to ‘1’, thecurrent Auxiliary Video Information (AVI) InfoFrame used on the HDMIport is indicated. The newly defined audio information fields include aversion field, an audio_coding_type field, an audio_channel_count field,a sampling_frequency field, a sample_size field, a max_bit_rate field, aspeaker_allocation field, a down_mix field, and a level_shift_valuefield.

The version field indicates an AUDIO InfoFrame version. And, theaudio_coding_type field indicates the audio coding type associated withthe audio on the HDMI link. For example, each value indicates thefollowing:

-   -   0000₂=Refer to stream header;    -   0001₂=IEC60958 PCM;    -   0010₂=AC-3;    -   0011₂=MPEG1 (Layers 1 & 2);    -   0100₂=MP3 (MPEG1 Layer 3);    -   0101₂=MPEG2 (multichannel);    -   0110₂=AAC;    -   0111₂=DTS;    -   1000₂=ATRAC; and    -   others=reserved.

The audio_channel_count field indicates the audio channel countassociated with the audio on the HDMI link. For example, each valueindicates the following:

-   -   000₂=Refer to stream header;    -   001₂=2ch;    -   010₂=3ch;    -   011₂=4ch;    -   100₂=5ch;    -   101₂=6ch;    -   110₂=7ch; and    -   111₂=8ch.

The sampling_frequency field indicates the sampling frequency countassociated with the audio on the HDMI link. For example, each valueindicates the following:

-   -   000₂=Refer to stream header;    -   001₂=32 kHz;    -   010₂=44.1 kHz (CD);    -   011₂=48 kHz;    -   100₂=88.2 kHz;    -   101₂=96 kHz;    -   110₂=176.4 kHz; and    -   111₂=192 kHz.

The sample_size field indicates the sample size associated with theaudio on the HDMI link. For example, each value indicates the following:

-   -   00₂=Refer to stream header;    -   01₂=16 bit;    -   10₂=20 bit; and    -   11₂=24 bit.

The max_bit_rate field indicates the maximum bit rate associated withthe audio on the HDMI link. The speaker_allocation field indicates thespeaker allocation associated with the audio on the HDMI link. And, thedown_mix field indicates the down mix associated with the audio on theHDMI link. For example, each value indicates the following:

-   -   0₂=Permitted or no information about any assertion of this; and    -   1₂=Prohibited.

The level_shift_value field indicates the level shift value associatedwith the audio on the HDMI link. Herein, the level_shift_value fielduses the dB unit. Meanwhile, when a logical product (or logicalmultiplication, logical AND) between the auxiliary_information_statusfield value and 0x04 is equal to ‘1’, the current Source ProductDescription (SPD) information used within the HDMI port is created byusing the next newly defined SPD information fields within the SPD_info{} syntax. In other words, when a logical product (or logicalmultiplication, logical AND) between the auxiliary_information_statusfield value and 0x04 is equal to ‘1’, the current SPD InfoFrame used onthe HDMI port is indicated. The newly defined SPD information fieldsinclude a version field, a source_device_info field,vendor_name_character1 to vendor_name_character8 fields, andproduct_description_char1 to product_description_char16 fields.

The version field indicates an SPD InfoFrame version. Thesource_device_info field indicates the source device informationassociated with the source product description format on the HDMI link.For example, each value indicates the following:

-   -   00 _(h)=unknown;    -   01 _(h)=Digital STB;    -   02 _(h)=DVD;    -   03 _(h)=D-VHS;    -   04 _(h)=HDD Video;    -   05 _(h)=DVC;    -   06 _(h)=DSC;    -   07 _(h)=Video CD;    -   08 _(h)=Game;    -   09 _(h)=PC general; and    -   others=reserved.

The vendor_name_character1˜8 fields each indicates the vendor namecharacter associated with the source product description format on theHDMI link. These fields correspond to a 7 bit ASCII code. And, theproduct_description_char1˜16 fields each indicates the productdescription character associated with the source product descriptionformat on the HDMI link. These fields also correspond to a 7 bit ASCIIcode. Meanwhile, when a logical product (or logical multiplication,logical AND) between the auxiliary_information_status field value and0x08 is equal to ‘1’, the current MPEG information used within the HDMIport is created by using the next newly defined MPEG information fieldswithin the MPEG_info{ } syntax. In other words, when a logical product(or logical multiplication, logical AND) between theauxiliary_information_status field value and 0x08 is equal to 1′, thecurrent MPEG InfoFrame used on the HDMI port is indicated. Herein, thenewly defined MPEG information fields include a version field,mpeg_bit_rate0 to mpeg_bit_rate3 fields, a field_repeat field, and ampeg_frame field.

The version field indicates an MPEG source InfoFrame version. And, thempeg_bit_rate0˜3 fields each indicates the MPEG bit rate associated withthe MPEG source on the HDMI link. The MPEG bit rate is stored as 32 bitsand is expressed in Hz units. The mpeg_bit_rate0 field includes theleast significant byte, whereas the mpeg_bit_rate3 field includes themost significant byte. If the MPEG rate is unknown, or if the field isnot applied, all of the bits within the mpeg_bit_rate0˜3 fields are setto ‘0’. For example:

-   -   If, 10 Mbps→10,000,000 Hz (dec.)→0x 00 98 96 80 (hex.) Upper,        Lower Byte,    -   mpeg_bit_rate0 0x80 Lower Byte;    -   mpeg_bit_rate1 0x96;    -   mpeg_bit_rate2 0x98; and    -   mpeg_bit_rate3 0x00 Upper.

The field_repeat field indicates the field repeat for 3:2 pull-downassociated with the MPEG source on the HDMI link. For example, eachvalue indicates the following:

-   -   0₂=New field (or picture); and    -   1₂=Repeated field.

The mpeg_frame field indicates the MPEG frame associated with the MPEGsource on the HDMI link. For example, each value indicates thefollowing:

-   -   00₂=unknown (no data);    -   01₂=I Picture;    -   10₂=B Picture; and    -   11₂=P Picture.

Meanwhile, when a logical product (or logical multiplication, logicalAND) between the auxiliary_information_status field value and 0x10 isequal to ‘1’, the current General Control (GC) information used withinthe HDMI port is created by using the next newly defined GC informationfields within the GC_info{ } syntax. In other words, when a logicalproduct (or logical multiplication, logical AND) between theauxiliary_information_status field value and 0x10 is equal to ‘1’, thecurrent GC InfoFrame used on the HDMI port is indicated. The newlydefined GC information fields include a version field, and a cp_bytefield. The version field indicates a GC InfoFrame version. And, thecp_byte field indicates the cp byte associated with the general controlpacket on the HDMI link. For example, each value indicates thefollowing:

-   -   0₂=Set Audio/Video Mute; and    -   1₂=Clear Audio/Video Mute.

As described above, all of the status information for the DVI links orthe HDMI links that are connected to the host is created by using theDVI/HDMI Status Report Syntax. Herein, the number and content of thefields that are newly defined in FIG. 4 only correspond to a preferredembodiment of the present invention. Therefore, since variations andmodifications may be made by the author (or designer) of the standardand of the system, the present invention is not limited to the proposedembodiments described herein. Furthermore, the contents defined for eachvalue in each of the fields correspond only to the preferred embodimentof the present invention and are not limited to the embodimentsdescribed herein.

Referring to FIG. 4A to 4C, the host verifies all of the DVI and HDMIlink statuses and creates a HDMI_DVI Status Report Syntax that is to bereported to the POD module. First of all, whether or not a DVI/HDMI linkexists is indicated in the connection_status field value. Thereafter,when the connection_status field value is not equal to ‘0’, i.e., whenat least one or more DVI/HDMI links exist, the number of DVI/HDMI linksexisting within the host is indicated in the connection_status field.Subsequently, the FOR loop is repeated as much as the number indicatedin the connection_status field. Each time the FOR loop is performed, astatus information of the DVI link or the HDMI link is created.

FIG. 5 illustrates an example of a digital cable TV receiver including aDVI/HDMI controller according to the present invention. The digitalcable TV receiver broadly includes a host 100, and a POD module 200 thatcan be mounted to or dismounted (or separated) from a slot of the host100. The host 100 may either be used to receive cable broadcast programsonly or be used to receive all types of broadcast programs includingcable broadcast programs, ground wave (or terrestrial) broadcastprograms, and satellite broadcast programs. FIG. 5 illustrates anexample of a cable digital television that can receive both cable andground wave broadcast programs.

In addition, there are two types of data broadcast program transmissionmethods, wherein data broadcast programs such as stocks information orweather forecast are transmitted. More specifically, an Out Of Band(OOB) method and a DOCSIS Set-top Gateway (DSG) method are proposed as amethod for upstream services within an open cable. The data broadcastprogram may be viewed at the moment a viewer views the television (TV)and selects a desired program. Alternatively, the data broadcast programmay be viewed when the viewer directly interacts with the broadcastprogram or when the viewer selects the information he or she needs. TheOOB method is most commonly used in the United States, and the DSGmethod is most commonly used in the Republic of Korea. However, inKorea, discussion is still under process as to which type of method isto be selected as the Korean standard. Herein, the types of method thatare under discussion include the OOB-only method, the OOB/DSG combinedmethod, the DSG-only method, etc.

The OOB method is a standard that defines a transmission standardbetween intersect equipments within a cable broadcast station (head-end)and a Set-Top box. The DSG method relates to a transmission methodbetween a cable modem control system of a cable broadcast station and aDOCSIS-based cable modem within a Set-Top box. The DOCSIS refers to adigital cable TV standard adopted by CableLabs, which is a U.S. cablebroadcast standard certification organization. The DOCSIS standard usescable modem to allow data to be transmitted. The example of a digitalcable TV receiver using the OOB/DSG combined method is shown in FIG. 5.However, this is only one of the preferred embodiments of the presentinvention, and one of an OOB-only digital cable TV receiver and aDSG-only digital cable TV receiver may be used according to the presentinvention.

FIG. 6 illustrates a flow chart of process steps for creating andtransmitting DVI/HDMI status information according to the presentinvention. Hereinafter, an embodiment according to the present inventionwill now be described with reference to FIG. 2 to FIG. 6. Morespecifically, in the host 100, a tuner 101 tunes only a specific channelfrequency from ground wave Audio/Video (A/V) broadcasting, which istransmitted through an antenna, and cable A/V broadcasting, which istransmitted by In-band through a cable. Then, the tuned channelfrequency is transmitted to a first demodulator 102. Since each of theground wave broadcasting and the cable broadcasting has a differenttransmission method, each of the decoding methods within the firstdemodulator 102 is also different from one another. In other words, theground wave A/V broadcasting is demodulated to a Vestigial Sideband(VSB) Modulation method and transmitted accordingly, and the cable A/Vbroadcasting is demodulated to a Quadrature Amplitude Modulation (QAM)method and transmitted accordingly. Therefore, when the channelfrequency tuned from the tuner 101 is a ground wave broadcast channelfrequency, the tuned channel frequency is demodulated to a VSB methodfrom the first demodulator 102. Alternatively, when the channelfrequency tuned from the tuner 101 is a cable broadcast channelfrequency, the tuned channel frequency is demodulated to a QAM methodfrom the first demodulator 102.

In case of the ground wave broadcasting, the demodulated signaltransmitted from the first demodulator 102 is transmitted to ademultiplexer 103. And, in case of the cable broadcasting, thedemodulated signal is transmitted to the demultiplexer 103 through thePOD module 200 mounted on the slot. The POD module 200 includes aConditional Access (CA) system for preventing high value-added broadcastcontents from being copied and for providing restricted access. The PODmodule 200 is also referred to as a cable card. When a scramble occursin the cable A/V broadcasting, the POD module descrambles the cable A/Vbroadcasting, which is then transmitted to the demultiplexer 103. Whenthe POD module 200 is not inserted in the slot, the cable A/Vbroadcasting demodulated from the first demodulator 102 is directlytransmitted to the demultiplexer 103. In this case, the scrambled cableA/V broadcasting cannot be descrambled, and therefore the viewers areunable to view the broadcast program normally.

The demultiplexer 103 receives the multiplexed signal and separates themultiplexed signal to a video signal and an audio signal. Thereafter,the demultiplexer 103 transmits the separated signals to a decoder 104.The decoder 104 recovers the compressed A/V signal to its initial stateby using a video decoding algorithm and an audio decoding algorithm,respectively, and then outputs the recovered signal for display.Meanwhile, a second tuner 105 tunes a specific channel frequency amongthe data broadcasting transmitted through cable by the DSG method andtransmits the tuned channel frequency to a second demodulator 106. Thesecond demodulator 106 demodulates the DSG type data broadcasting, whichis then transmitted to a CPU 110. Moreover, a third tuner 107 tunes aspecific channel frequency among the data broadcasting transmittedthrough cable by the OOB method and transmits the tuned channelfrequency to a third demodulator 111. The third demodulator 111demodulates the OOB type data broadcasting by using a Quartenary PhaseShift Key (QPSK) method, which is then transmitted to the POD module200. More specifically, since the OOB type uses the QPSK transmissionmethod, a receiving end also uses a QPSK type modulation.

Furthermore, when a bi-directional telecommunication between the cablebroadcast station (or cable TV station) and the cable broadcast programreceiver (or digital cable TV receiver) can be performed, theinformation (e.g., paid program subscription, Diagnostic information ofthe host, etc.) transmitted from the cable broadcast program receiver tothe cable broadcast station is transmitted by one of the OOB method andthe DSG method. This is why a switching unit 108 is provided herein.More specifically, when the OOB type transmission is used, userinformation or System Diagnostic information is transmitted to amodulator 109 through the POD module 200 and the switching unit 108.Then, the information is modulated by using the QPSK method from themodulator 109, which is then transmitted to the cable broadcast stationthrough cable. On the other hand, when using the DSG type transmission,the information is transmitted to the modulator 109 through the CPU 110and the switching unit 108. Thereafter, the information is modulated byusing a QAM-16 method from the modulator 109, which is then transmittedto the cable broadcast station through cable.

Meanwhile, the CPU 110 parses the Diagnostic_req APDU, which istransmitted from the POD module 200 (S201). Then, the CPU 110 verifieswhether ‘0x08’ is included within the Diagnostic ID (S202). When the0x08 is included, the DVI/HDMI status is verified by using a DVI/HDMIcontroller 120, and the verified result is created, as shown in FIGS. 4Ato 4C, and is transmitted to the POD module 200. More specifically, theDVI/HDMI controller 120 first verifies whether peripheral devices areconnected to the host by DVI/HDMI link and also verifies the number ofthe connected peripheral devices, so as to set up (or determine) theconnection_status field value and the connection_count field value.Subsequently, the DVI/HDMI controller 120 determines whether theconnection_status field value is ‘0’ (S203). When the connection_statusfield value is ‘0’, there are no peripheral devices connected to thehost by DVI/HDMI link. Accordingly, the process step is skipped to Step207, thereby transmitting a Diagnostic_cnf APDU to the POD module 200,which indicates that no DVI/HDMI status information is included.

In the above-described Step 203, when the connection_status field valueis not ‘0’, at least one peripheral device is connected to the host byDVI/HDMI link, and so the process step proceeds to Step 204. Thereafter,a variable i is initialized to ‘0’ so as to determine whether the valueof the variable i is lower (or smaller) than the connection_count fieldvalue (S205). The variable i is a value that is compared with theconnection_count field value in order to transmit all of the DVI/HDMIlink status information of more than one peripheral devices to the PODmodule. Herein, the variable i is increased by ‘1’ each time the FORloop is performed. Therefore, in the above-described Step 205, when thevalue of the variable i is lower than the connection_count field value,this indicates that there still remain DVI/HDMI link status informationwhich have not been transmitted to the POD module 200. At this point,the process proceeds to Step 206, wherein the connection_no field, theconnection_mode field, the connection_type field, the host_HDCP_statusfield, the device_HDCP_status field, and the video format informationare created. The video format information includes horizontal_linesinformation, vertical_lines information, scan_rate information,aspect_ratio information, and prog_inter_type information. Moreover,when the connection_mode field value is not equal to ‘0’, i.e., when thecurrent status information is the status information for a HDMI link, anauxiliary_information_status field value is created, and the AVIinformation, the AUDIO information, the SPD information, the MPEGinformation, and the GC information that are associated with the HDMIlink are also created in accordance with theauxiliary_information_status field value. In other words, theabove-described Step 204 to Step 206 correspond to the FOR looprepetition statement of FIG. 4.

Furthermore, in the above-described Step 205, when the value of the ivariable is determined to be lower than the connection_count fieldvalue, this indicates that all status information for the DVI/HDMIlinks, which will be transmitted to the POD module 200, is created. Andso, the process proceeds to Step 207. The status information for all ofthe DVI/HDMI links of the host, which is created each time the FOR loopis performed, is included in the Diagnostic_cnf APDU, which is thentransmitted to the POD module 200.

As described above, the process of creating and transmitting DVI/HDMIstatus information may either be performed by using hardware orperformed by using middleware or software. Also, the DVI/HDMI controller120 may either be included in the CPU 110 or formed externally, as shownin FIG. 5. In the above-described embodiment of the present invention,the POD module uses a Diagnostic ID in order to request the host todiagnose all statuses for the DVI/HDMI links. And, the host verifies allstatus information of the DVI links and the HDMI links and transmits thecorresponding results to the POD module.

Meanwhile, in another embodiment of the present invention, the GenericDiagnostic Protocol may be expanded so that a Diagnostic ID is assignedfor each of the DVI Diagnostic and the HDMI Diagnostic. Thus, a requestfor each of the DVI Diagnostic and the HDMI Diagnostic may bedistinguished (or identified) from one another and separatelytransmitted to the POD module. Then, in accordance with the receivedDiagnostic ID, the host may verify only one of the DVI statusinformation and the HDMI status information and transmit the verifiedresult to the POD module. Table 3 and Table 4 show each Diagnostic itemdefined in the expanded Generic Diagnostic Protocol and the DiagnosticIDs assigned for each Diagnostic item. TABLE 3 Diagnostic ID Diagnostic00 Set-Top memory allocation 01 Software version 02 Firmware version 03MAC status 04 FAT status 05 FDC status 06 Current Channel Report 07 1394Port 08 DVI status

0A˜FF Reserved for future use

TABLE 4 Diagnostic ID Diagnostic 00 Set-Top memory allocation 01Software version 02 Firmware version 03 MAC status 04 FAT status 05 FDCstatus 06 Current Channel Report 07 1394 Port 08 DVI status

0B˜FF Reserved for future use

More specifically, in Table 3 and Table 4, the Diagnostic ID and itemmarked in bold italic characters are newly defined within the GenericDiagnostic Protocol according to the present invention. In Table 3, whenthe Diagnostic ID is 0x08, the host verifies the DVI status andtransmits the verified result to the POD module. On the other hand, whenthe Diagnostic ID is 0x09, the host verifies the HDMI status andtransmits the verified result to the POD module. In Table 4, a newdefinition for verifying the status of all DVI/HDMI links by using asingle Diagnostic ID is added to Table 3. At this point, ‘0A’ isassigned as the newly defined Diagnostic ID. In the above-describedTable 3 and Table 4, the Diagnostic ID for the HDMI being assigned as‘09’ and the Diagnostic ID for the DVI/HDMI being assigned as ‘0A’ areonly details of a preferred embodiment of the present invention. Theauthor (or designer) of the standard and of the system may choose toassign other reserved ID values other than ‘09’ and ‘0A’ as theDiagnostic ID, which is not limited to the values proposed in theabove-described embodiments of the present invention. Furthermore, whenthe POD module requests only the HDMI status to be diagnosed, and whenthe host verifies the status information for all HDMI links only andtransmits the verified results to the POD module, the DVI/HDMIcontroller of the digital cable TV receiver shown in FIG. 5 may bereplaced with a HDMI controller.

FIGS. 7A to 7C illustrate an example of a HDMI Status Report Syntax ofthe Generic Diagnostic Protocol, which is created when the POD modulerequests a Diagnostic of the HDMI status. More specifically, the HDMIStatus Report Syntax of FIGS. 7A to 7C is configured by deleting theconnection_mode field shown in FIGS. 4A to 4C and by deleting the linefor comparing whether the connection_mode field value is equal to ‘1’.Also, the description for each of the fields of the HDMI Status ReportSyntax is identical to those described in FIGS. 4A to 4C and will,therefore, be omitted for simplicity. At this point, theconnection_status field, the host_HDCP_status field, theDevice_HDCP_status field, the video_format field, the horizontal_linesfield, the vertical_lines field, the scan_rate field, the aspect_ratiofield, and the prog_inter_type field creates only the informationassociated with the HDMI link.

FIG. 8 illustrates a flow chart of process steps for creating andtransmitting HDMI status information according to another embodiment ofthe present invention. More specifically, the CPU 110 parses theDiagnostic_req APDU, which is transmitted from the POD module 200(S301). Then, the CPU 110 verifies whether ‘0x09’ is included within theDiagnostic ID (S302). When the 0x09 is included, the HDMI status isverified, and the verified result is transmitted to the POD module 200.In other words, whether or not peripheral devices are connected to thehost by HDMI link is verified, and the number of the connectedperipheral devices is also verified, so as to set up (or determine) theconnection_status field value and the connection_count field value.Thereafter, whether or not the connection_status field value is ‘0’ isverified (S303). When the connection_status field value is ‘0’, thereare no peripheral devices connected to the host by HDMI link.Accordingly, the process step is skipped to Step 307, therebytransmitting a Diagnostic_cnf APDU to the POD module 200, whichindicates that no HDMI status information is included.

In the above-described Step 303, when the connection_status field valueis not ‘0’, at least one peripheral device is connected to the host byHDMI link, and so the process step proceeds to Step 304. Thereafter, avariable i is initialized to ‘0’ so as to determine whether the value ofthe variable i is lower (or smaller) than the connection_count fieldvalue (S305). The variable i is a value that is compared with theconnection_count field value in order to transmit all of the HDMI linkstatus information of more than one peripheral devices to the POD module200. Herein, the variable i is increased by ‘1’ each time the FOR loopis performed. Therefore, in the above-described Step 305, when the valueof the variable i is lower than the connection_count field value, thisindicates that there still remain HDMI link status information whichhave not been transmitted to the POD module 200. At this point, theprocess proceeds to Step 306, wherein the connection_no field, theconnection_type field, the host_HDCP_status field, thedevice_HDCP_status field, and the video format information are created.Herein, the video format information includes horizontal_linesinformation, vertical_lines information, scan_rate information,aspect_ratio information, and prog_inter_type information. Thereafter,an auxiliary_information_status field value is created, and the AVIinformation, the AUDIO information, the SPD information, the MPEGinformation, and the GC information that are associated with the HDMIlink are also created in accordance with theauxiliary_information_status field value. In other words, theabove-described Step 304 to Step 306 correspond to the FOR looprepetition statement of FIG. 7.

Meanwhile, in the above-described Step 305, when the value of the ivariable is determined to be lower than the connection_count fieldvalue, this indicates that all status information for the HDMI links,which will be transmitted to the POD module 200, is created. And so, theprocess step proceeds to Step 307. The status information for all of theHDMI links of the host, which is created each time the FOR loop isperformed, is included in the Diagnostic_cnf APDU, which is thentransmitted to the POD module 200.

As described above, the present invention may be applied to all types oftelevision receivers and Set-Top boxes supporting cable broadcastprograms. Most particularly, the present invention can be applied to alltypes of digital cable TV receivers adopting the SCTE 28 standard.Meanwhile, preferred embodiments have been proposed in the descriptionof the present invention. Therefore, when considering the technicaldifficulty of the present invention, those skilled in the art are fullycapable of modifying the present invention so as to propose otherembodiments of the present invention. Evidently, it will be apparentthat such modifications do not depart from the scope and spirit of thepresent invention.

In the above described digital cable TV receiver, diagnosis method forthe same, and data structure of the HDMI status report according to thepresent invention, the POD module may request the host to verify andreport the HDMI status, and the host may verify the HDMI statusinformation and transmit the verified result to the POD module. Thus,the host may transmit not only the DVI status information but also theHDMI status information to the POD module. Furthermore, the presentinvention expands an Diagnostic ID and a Diagnostic Status Report Syntaxwithin a Generic Diagnostic Protocol defined in the SCTE 28 standard, soas to create the status information for all of the DVI links and theHDMI links for the connections within the host and to transmit thestatus information to the POD module, thereby facilitating the expansionand providing compatibility of the Diagnostic ID and the DiagnosticStatus Report Syntax, so that it can be applied to all types of digitalcable TV receivers adopting the SCTE 28 standard.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

1. A digital cable TV receiver, comprising: a POD module; and a hostdevice comprising a controller and a HDMI port linked to a peripheraldevice, wherein the controller generates a HDMI status report andtransmits the HDMI status report to the POD module when a diagnosticrequest for HDMI status is received from the POD module, the HDMI statusreport comprising HDMI status information associated with the peripheraldevice.
 2. The digital cable TV receiver of claim 1, wherein the HDMIstatus information comprises a connection type field identifying theHDMI port as any one of an input port, an output port, and aninput/output port.
 3. The digital cable TV receiver of claim 1, whereinthe HDMI status information comprises a host HDCP status fieldindicating whether HDCP is enabled on the HDMI port and a device HDCPstatus field indicating a HDCP status of the peripheral device connectedto the HDMI port.
 4. The digital cable TV receiver of claim 1, whereinthe HDMI status information comprises video format informationindicating a current video format utilized on the HDMI port.
 5. Thedigital cable TV receiver of claim 4, wherein the video formatinformation comprises at least one of a number of horizontal lines, anumber of vertical lines, a scan rate, an aspect ratio, and a scanningtype associated with the current video format.
 6. The digital cable TVreceiver of claim 1, wherein the HDMI status information comprises atleast one of AVI information indicating a current Auxiliary VideoInformation InfoFrame utilized on the HDMI port, audio informationindicating a current Audio InfoFrame utilized on the HDMI port, SPDinformation indicating a current Source Product Description InfoFrameutilized on the HDMI port, and MPEG information indicating a currentMPEG source InfoFrame utilized on the HDMI port.
 7. A digital cable TVreceiver, comprising: a POD module; and a host device comprising acontroller and a plurality of HDMI ports linked to a plurality ofperipheral devices, respectively, wherein the controller generates aHDMI status report and transmits the HDMI status report to the PODmodule when a diagnostic for HDMI status is received from the PODmodule, the HDMI status report comprising a plurality of HDMI statusinformation associated with the plurality of peripheral devices,respectively.
 8. The digital cable TV receiver of claim 7, wherein theHDMI status report further comprises a connection count field indicatinga total number of the plurality of HDMI ports linked to the plurality ofperipheral devices.
 9. The digital cable TV receiver of claim 7, whereineach HDMI status information comprises a connection number fieldindicating an index number of a HDMI port linked to a peripheral device.10. The digital cable TV receiver of claim 7, wherein each HDMI statusinformation comprises at least one of AVI information indicating acurrent Auxiliary Video Information InfoFrame utilized on the HDMI port,audio information indicating a current Audio InfoFrame utilized on theHDMI port, SPD information indicating a current Source ProductDescription InfoFrame utilized on the HDMI port, and MPEG informationindicating a current MPEG source InfoFrame utilized on a correspondingHDMI port.
 11. A diagnostic method for a digital cable TV receiver, themethod comprising: receiving a diagnostic request for HDMI status from aPOD module; and performing a diagnostic function in response to thediagnostic request by generating a HDMI status report and transmittingthe HDMI status report to the POD module, the HDMI status reportcomprising HDMI status information associated with a peripheral devicewhich is linked to a HDMI port.
 12. The diagnostic method of claim 11,wherein the HDMI status information comprises a connection type fieldidentifying the HDMI port as any one of an input port, an output port,and an input/output port.
 13. The diagnostic method of claim 11, whereinthe HDMI status information comprises a host HDCP status fieldindicating whether HDCP is enabled on the HDMI port and a device HDCPstatus field indicating a HDCP status of the peripheral device connectedto the HDMI port.
 14. The diagnostic method of claim 11, wherein theHDMI status information comprises video format information indicating acurrent video format utilized on the HDMI port.
 15. The diagnosticmethod of claim 14, wherein the video format information comprises atleast one of a number of horizontal lines, a number of vertical lines, ascan rate, an aspect ratio, and a scanning type associated with thecurrent video format.
 16. The diagnostic method of claim 11, wherein theHDMI status information comprises at least one of AVI informationindicating a current Auxiliary Video Information InfoFrame utilized onthe HDMI port, audio information indicating a current Audio InfoFrameutilized on the HDMI port, SPD information indicating a current SourceProduct Description InfoFrame utilized on the HDMI port, and MPEGinformation indicating a current MPEG source InfoFrame utilized on theHDMI port.
 17. A diagnostic method for a digital cable TV receiver, themethod comprising: receiving a diagnostic request for HDMI status from aPOD module; and performing a diagnostic function in response to thediagnostic request by generating a HDMI status report and transmittingthe HDMI status report to the POD module, the HDMI status reportcomprising a plurality of HDMI status information associated with aplurality of peripheral devices which are linked to a plurality of HDMIports, respectively.
 18. The diagnostic method of claim 17, wherein theHDMI status report further comprises a connection count field indicatinga total number of the plurality of HDMI ports linked to the plurality ofperipheral devices.
 19. The diagnostic method of claim 17, wherein eachHDMI status information comprises a connection number field indicatingan index number of a HDMI port linked to a peripheral device.
 20. Thediagnostic method of claim 17, wherein each HDMI status informationcomprises at least one of AVI information indicating a current AuxiliaryVideo Information InfoFrame utilized on the HDMI port, audio informationindicating a current Audio InfoFrame utilized on the HDMI port, SPDinformation indicating a current Source Product Description InfoFrameutilized on the HDMI port, and MPEG information indicating a currentMPEG source InfoFrame utilized on a corresponding HDMI port.
 21. A datastructure of a HDMI status report for use in a digital cable TVreceiver, the data structure comprising: a connection status fieldindicating whether a connection exists on a HDMI port; and HDMI statusinformation associated with a peripheral device linked to the HDMI port.22. The data structure of claim 21, wherein the HDMI status informationcomprises a connection type field identifying the HDMI port as any oneof an input port, an output port, and an input/output port.
 23. The datastructure of claim 21, wherein the HDMI status information comprises ahost HDCP status field indicating whether HDCP is enabled on the HDMIport and a device HDCP status field indicating a HDCP status of theperipheral device connected to the HDMI port.
 24. The data structure ofclaim 21, wherein the HDMI status information comprises video formatinformation indicating a current video format utilized on the HDMI port.25. The data structure of claim 24, wherein the video format informationcomprises at least one of a number of horizontal lines, a number ofvertical lines, a scan rate, an aspect ratio, and a scanning typeassociated with the current video format.
 26. The data structure ofclaim 21, wherein the HDMI status information comprises at least one ofAVI information indicating a current Auxiliary Video InformationInfoFrame utilized on the HDMI port, audio information indicating acurrent Audio InfoFrame utilized on the HDMI port, SPD informationindicating a current Source Product Description InfoFrame utilized onthe HDMI port, and MPEG information indicating a current MPEG sourceInfoFrame utilized on the HDMI port.
 27. A data structure of a HDMIstatus report for use in a digital cable TV receiver, the data structurecomprising: a connection count field indicating a total number of aplurality of HDMI ports linked to a plurality of peripheral devices,respectively; and a plurality of HDMI status information associated withthe plurality of peripheral devices, respectively.
 28. The datastructure of claim 27, further comprising a connection status fieldindicating whether a connection exists on any one of the plurality ofHDMI ports.
 29. The data structure of claim 27, wherein each HDMI statusinformation comprises a connection number field indicating an indexnumber of a HDMI port linked to a peripheral device.
 30. The datastructure of claim 27, wherein each HDMI status information comprises atleast one of AVI information indicating a current Auxiliary VideoInformation InfoFrame utilized on the HDMI port, audio informationindicating a current Audio InfoFrame utilized on the HDMI port, SPDinformation indicating a current Source Product Description InfoFrameutilized on the HDMI port, and MPEG information indicating a currentMPEG source InfoFrame utilized on a corresponding HDMI port.
 31. Adigital cable TV receiver, comprising: a POD module; and a host devicecomprising a controller, a HDMI port linked to a first peripheraldevice, and a DVI port linked to a second peripheral device, thecontroller generating a HDMI/DVI status report and transmits theHDMI/DVI status report to the POD module when a diagnostic request forHDMI/DVI status is received from the POD module, the HDMI/DVI statusreport comprising HDMI status information associated with the firstperipheral device and DVI status information associated with the secondperipheral device.
 32. The digital cable TV receiver of claim 31,wherein the HDMI status information comprises a connection mode fieldindicating that a HDMI connection exists on the HDMI port.
 33. Thedigital cable TV receiver of claim 31, wherein the DVI statusinformation comprises a connection mode field indicating that a DVIconnection exists on the DVI port.
 34. The digital cable TV receiver ofclaim 31, wherein the HDMI status information comprises at least one ofAVI information indicating a current Auxiliary Video InformationInfoFrame utilized on the HDMI port, audio information indicating acurrent Audio InfoFrame utilized on the HDMI port, SPD informationindicating a current Source Product Description InfoFrame utilized onthe HDMI port, and MPEG information indicating a current MPEG sourceInfoFrame utilized on the HDMI port.
 35. A diagnostic method for adigital cable TV receiver, the method comprising: receiving a diagnosticrequest for HDMI/DVI status from a POD module; and performing adiagnostic function in response to the diagnostic request by generatinga HDMI/DVI status report and transmitting the HDMI/DVI status report tothe POD module, the HDMI/DVI status report comprising HDMI statusinformation associated with a first peripheral device which is linked toa HDMI port and DVI status information associated with a secondperipheral device which is linked to a DVI port.
 36. The diagnosticmethod of claim 35, wherein the HDMI status information comprises aconnection mode field indicating that a HDMI connection exists on theHDMI port.
 37. The diagnostic method of claim 35, wherein the DVI statusinformation comprises a connection mode field indicating that a DVIconnection exists on the DVI port.
 38. The diagnostic method of claim35, wherein the HDMI status information comprises at least one of AVIinformation indicating a current Auxiliary Video Information InfoFrameutilized on the HDMI port, audio information indicating a current AudioInfoFrame utilized on the HDMI port, SPD information indicating acurrent Source Product Description InfoFrame utilized on the HDMI port,and MPEG information indicating a current MPEG source InfoFrame utilizedon the HDMI port.
 39. A data structure of a HDMI/DVI status report foruse in a digital cable TV receiver, the data structure comprising: aconnection status field indicating whether a connection exists on anyone of a HDMI port and a DVI port; HDMI status information associatedwith a first peripheral device linked to the HDMI port; and DVI statusinformation associated with a second peripheral device linked to the DVIport.
 40. The data structure of claim 39, wherein the HDMI statusinformation comprises a connection mode field indicating that a HDMIconnection exits on the HDMI port.
 41. The data structure of claim 39,wherein the DVI status information comprises a connection mode fieldindicating that a DVI connection exists on the DVI port.
 42. The datastructure of claim 39, wherein the HDMI status information comprises atleast one of AVI information indicating a current Auxiliary VideoInformation InfoFrame utilized on the HDMI port, audio informationindicating a current Audio InfoFrame utilized on the HDMI port, SPDinformation indicating a current Source Product Description InfoFrameutilized on the HDMI port, and MPEG information indicating a currentMPEG source InfoFrame utilized on the HDMI port.